Skip to main content

Your data has issues

There is a problem

  • geometry column must have valid geometry
Reference Name Tree preservation order Uprn Address text Point Geometry Notes Organisation Felled date Entry date Start date End date
801 K28 ELGIN CRESCENT

Unexpected geom type

2025-01-03
802 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
803 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
804 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
805 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
806 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
807 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
808 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
809 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
810 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
811 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
812 K18 ELGIN CRESCENT

Unexpected geom type

2025-01-03
813 K24 ELGIN CRESCENT

Unexpected geom type

2025-01-03
814 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
815 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
816 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
817 K12 ELGIN CRESCENT

Unexpected geom type

2025-01-03
818 K12 ELGIN CRESCENT

Unexpected geom type

2025-01-03
819 K12 ELGIN CRESCENT

Unexpected geom type

2025-01-03
820 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
821 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
822 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
823 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
824 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
825 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
826 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
827 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
828 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
829 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
830 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
831 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
832 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
833 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
834 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
835 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
836 Jan-74 ELGIN CRESCENT

Unexpected geom type

2025-01-03
837 K19 ELGIN CRESCENT

Unexpected geom type

2025-01-03
838 Sep-81 ELGIN CRESCENT

Unexpected geom type

2025-01-03
839 Sep-77 ELGIN CRESCENT

Unexpected geom type

2025-01-03
840 16/87 ELGIN CRESCENT

Unexpected geom type

2025-01-03
841 Jul-92 ELGIN CRESCENT

Unexpected geom type

2025-01-03
842 15/72 ELM PARK ROAD

Unexpected geom type

2025-01-03
843 15/72 ELM PARK ROAD

Unexpected geom type

2025-01-03
844 15/72 ELM PARK ROAD

Unexpected geom type

2025-01-03
845 15/72 ELM PARK ROAD

Unexpected geom type

2025-01-03
846 22/74 ELM PARK ROAD

Unexpected geom type

2025-01-03
847 22/74 ELM PARK ROAD

Unexpected geom type

2025-01-03
848 22/74 ELM PARK ROAD

Unexpected geom type

2025-01-03
849 22/74 ELM PARK ROAD

Unexpected geom type

2025-01-03
850 Aug-76 ELM PARK ROAD

Unexpected geom type

2025-01-03

Showing rows 801 to 850 of 1000

How to fix this issue

Your dataset is missing the geometry column.

The Tree guidance explains how to fix the issue:

geometry

The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.

If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).

You must provide a point or geometry for each tree. You may provide both.

Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...

If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL